C++test

General

Name: C++test
Tool Provider:

Parasoft Corporation
Supported Standards: DO178C DO330 EN50128 IEC61508 ISO26262
Description:

Parasoft’s C/C++test is the fully integrated software testing solution for embedded safety-critical industries.

Its automated software testing capabilities are also made for today’s high-velocity Agile DevOps environments. It integrates tightly into your C and C++ IDE, CI/CD pipeline and containerized deployments to detect defects earlier, and automatically enforce compliance with industry standards.
Use Cases:

Content

Identifications

C++ Version

Description:

C++Test Version 10.4.3

Parasoft C/C++test Professional

Version: 10.4.3.20191114B689

Eclipse feature version: 10.4.3.972
Configuration:

Standard Configuration
Environment:

Windows, Linux

C++Test version 10.4.3 must be on path.

Java 8 must be on path.

gcc/g++ ver. 7 (64 Bit) and cl.exe 14.1 (32 Bit) must be on path.

Use Cases

JSF Compliance

Description:

The "JSF Compliance" use case defines the set of C++test features required for achieving JSF Coding Standard compliance.

The following requirements are connected to this use case:

[PROJ] Importing / configuring a project

[TCFG] Test Configuration

[CS] Coding Standards Analysis

[FA] Flow Analysis

[REP] Reporting

The use case may need customization if environment specific adaptations are required.
Safety-Impact: yes
Inputs:
  • C/C++ source code:

    The C/C++ source code to be analyzed by C++Test
  • Executable object code:

    The executable object code to be analyzed
Outputs:
  • C++Test report:

    Report generated by the tool C++Test
Features:
  • Coding Standards Analysis:

    Requirements related to the coding standards analysis.
  • Importing / configuring project:

    Requirements related to creating / importing / configuring a project to test in Parasoft C++test.
  • Standards Compliance:

    To achieve compliance with industry coding standards

    Test Suite
  • Test Configuration:

    Requirements related to the C++test test configurations
Potential errors:
# Error Safety-Impact Mitigations for detections/avoidance Final detection/avoidance probability
1 [Coding Standards Analysis] Incorrect values from feature Coding Standards analysis

Values provided by features Coding Standards Analysis is incorrect

 impact_true HIGH
2 [Importing / configuring project] Incorrect values from feature Importing / configuring project

Values provided by feature Importing / configuring project are incorrect

 impact_true HIGH
3 [Standards Compliance] Incorrect values and violation report from feature Compliance

Values and violation report provided by feature compliance are incorrect

 impact_true HIGH
4 [Test Configuration] Incorrect values from feature Test Configuration

Values provided by feature Test Configuration are incorrect

 impact_true HIGH

MISRA C 2012 Compliance

Description:

The "MISRA C 2012 Compliance" use case defines the set of C++test features required for achieving MISRA C 2012 Coding Standard compliance.

The following requirements are connected to this use case:

[PROJ] Importing / configuring a project

[TCFG] Test Configuration

[CS] Coding Standards Analysis

[FA] Flow Analysis

[STD] Standards Compliance

[REP] Reporting

The use case may need customization if environment specific adaptations are required.
Safety-Impact: yes
Inputs:
  • C/C++ source code:

    The C/C++ source code to be analyzed by C++Test
  • Executable object code:

    The executable object code to be analyzed
Outputs:
  • C++Test report:

    Report generated by the tool C++Test

Static Analysis - Custom

Description:

The "Static Analysis - Custom" use case defines the set of C++test features required for running static code analysis with selected coding guidelines (rules).

The following requirements are connected to this use case:

[PROJ] Importing / configuring a project

[TCFG] Test Configuration

[CS] Coding Standards Analysis

[FA] Flow Analysis

[STD] Standards Compliance

[REP] Reporting

The use case may need customization if environment specific adaptations are required.
Safety-Impact: yes
Inputs:
  • C/C++ source code:

    The C/C++ source code to be analyzed by C++Test
  • Executable object code:

    The executable object code to be analyzed
Outputs:
  • C++Test report:

    Report generated by the tool C++Test

Unit Testing with Branch Coverage

Description:

The "Unit Testing with Branch Coverage" use case defines the set C++test features required for performing unit testing with the branch (decision) coverage metric.

The following requirements are connected to this use case:

[PROJ] Importing / configuring a project

[TCFG] Test Configuration

[UT] Unit Testing

[STUB] Stubs Module

[COV] Coverage Analysis

[REP] Reporting

The use case may need customization if environment specific adaptations are required.
Safety-Impact: yes
Inputs:
  • C/C++ source code:

    The C/C++ source code to be analyzed by C++Test
  • Executable object code:

    The executable object code to be analyzed
Outputs:
  • C++Test report:

    Report generated by the tool C++Test

Unit Testing with MCDC Coverage

Description:

The "Unit Testing with MCDC" use case defines the set C++test features required for performing unit testing with the MC/DC coverage metric.

The following requirements are connected to this use case:

[PROJ] Importing / configuring a project

[TCFG] Test Configuration

[UT] Unit Testing

[STUB] Stubs Module

[COV] Coverage Analysis

[REP] Reporting

The use case may need customization if environment specific adaptations are required.
Safety-Impact: yes
Inputs:
  • C/C++ source code:

    The C/C++ source code to be analyzed by C++Test
  • Executable object code:

    The executable object code to be analyzed
Outputs:
  • C++Test report:

    Report generated by the tool C++Test

Unit Testing with Statement Coverage

Description:

The "Unit Testing with Statement Coverage" use case defines the set of C++test features required for performing unit testing with the statement coverage metric.

The following requirements are connected to this use case:

[PROJ] Importing / configuring a project

[TCFG] Test Configuration

[UT] Unit Testing

[STUB] Stubs Module

[COV] Coverage Analysis

[REP] Reporting

The use case may need customization if environment specific adaptations are required.
Safety-Impact: yes
Inputs:
  • C/C++ source code:

    The C/C++ source code to be analyzed by C++Test
  • Executable object code:

    The executable object code to be analyzed
Outputs:
  • C++Test report:

    Report generated by the tool C++Test

Qualifications

Validas QKit

Description:

The QKit is a standard Validas QKit using QST and TAU that automatically executes the qualification tests in the user environment.

This qualification kit covers the C++ test tool and the following use case is considered:

JSF Compliance: defines the set of C++test features required for achieving JSF Coding Standard compliance.

Details on the planning and tests are removed for confidentiality reasons.
Qualfication method:

VALIDAS_QKIT
Identifications:
Use Cases:

Test suites and test cases

TestSuite for C++ test

Description:

This testsuite contains tests for use cases described in the model
Flags: Has Requirements Based Tests , Has Negative Tests , Has Boundary Tests , Has Equivalence Tests , Has Error Guessing Tests
Comment:

[details are removed for confidentiality reasons]
# tests: 807
Errors:
  • Incorrect values and violation report from feature Compliance
  • Incorrect values from feature Coverable Analysis

ManualTests

Description:

Test container for the manual test cases for use cases described in the model
Flags: Has Requirements Based Tests , Has Negative Tests , Has Boundary Tests , Has Equivalence Tests , Has Error Guessing Tests
# tests: 299
Errors:
  • Incorrect values from Flow Analysis
  • Incorrect values from Reporting mechanism features
  • Incorrect values from Stubs Module
  • Incorrect values from feature Coding Standards analysis
  • Incorrect values from feature Importing / configuring project
  • Incorrect values from feature Test Configuration
  • Incorrect values from feature Unit Testing
  • Incorrect values from features Command line interface and Graphical User Interface
  • Incorrect values provided by Application Monitoring

Mitigations

# Mitigation Detection/Avoidance probability Detected/Avoided errors
1 [Restriction] Do not use this feature - there are no validation test cases available

This feature has no tests, i.e. not testable. So don't use this feature.

 HIGH
  • Incorrect value from feature Metrics
  • Incorrect values from feature Code Duplication Detection